Add Community tag to plugins #2982
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Some post-facto feedback on this, if it leads somewhere I can move it to an issue. Please push back, but not a big fan of doing "Core Team" as this a) either gives me a vibe of a hobby project or b) is something that only an engineer that's familiar with OSS terminology will understand. I think it'd be better to do something that conveys an "official" vibe. Keeping it standardized maybe we could try something like we do for PostHog properties? Or maybe it's just as simple matter as changing the label.
Probably out of scope for this PR, but should there be a third category, something like community but verified? CC @mariusandra, @yakkomajuri just some thoughts |
|
Why not "Official" vs "Community"? |
|
Think that works well for now 👌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Please describe.
If this affects the frontend, include screenshots.
I guess this conflicts with #2965 but just bringing this up because it's important to differentiate core team vs community plugins here too so users are aware of what they're installing and we can be more liberal with accepting community plugins into the list.
Style is consistent with the website plugin library.
Checklist